<?php
/**
 * <https://y.st./>
 * Copyright © 2017 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'The Wix website-building tool is atrocious.',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<section id="general">
	<h2>General news</h2>
	<p>
		The touchpad on <a href="/en/domains/bailey.local.xhtml"><code>bailey</code></a> keeps getting stuck and not moving the cursor.
		After a bit of trying, it usually unsticks for me, but this might be a problem I&apos;ll be dealing with until the end of <code>bailey</code>&apos;s lifespan.
		That said, <code>bailey</code> also has a pointing stick that works perfectly, so if I don&apos;t have time to wait for the touchpad to start functioning again, I do have another option.
		I&apos;d use the pointing stick exclusively, but the touchpad&apos;s more convenient.
		I&apos;m not sure if that&apos;s because of the placement or because I&apos;m just in the habit of using a touchpad.
	</p>
	<p>
		My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
	</p>
</section>
<section id="university">
	<h2>University life</h2>
	<p>
		I finally got started on both discussion assignments today.
		I&apos;d planned to work on them early, but <a href="/en/domains/morgan.local.xhtml"><code>morgan</code></a> died on me early in the week.
		I wasn&apos;t even able to complete the reading assignments until today, let alone the discussion assignments!
	</p>
	<blockquote>
		<p>
			Like last week, no website articles were referenced in the reading assignment, so I&apos;ll reference the textbook instead.
		</p>
		<p>
			Modern operating systems are able to keep several applications running &quot;simultaneously&quot; by running each program a little at a time, saving the state, and switching to another program to run that one for a while.
			In regards to the $a[CPU], the process of divvying up $a[CPU] time in this manner is called &quot;time sharing&quot; (Arpaci-Dusseau &amp; Arpaci-Dusseau, 2016).
			Each process is given its own virtual $a[CPU], which it can use as if it were a real one.
			When the operating system gives $a[CPU] time to a program, it reawakens that program and runs the instructions given to the virtual $a[CPU] on the real $a[CPU].
			By quickly and cleverly alternating between applications, freezing and unfreezing them as needed, the operating system is able to give the user the appearance of running multiple programs at once, despite actually only running one at a time.
			As programs have gaps in their $a[CPU] use, such as when trying to write to or read from the disk, this switching also helps maximise the use of the processor.
			When an application starts an {$a['I/O']} operation, it has no more need of the $a[CPU] until that operation completes, so while the system works on completing the read or write, it lends the $a[CPU] to the next application.
			Meanwhile, as each program has its own, dedicated, virtual $a[CPU], the logic of $a[CPU]-sharing doesn&apos;t need to be written into every individual program.
			Applications can ignore the sharing and leave the heavy lifting in that area to the operating system.
		</p>
		<div class="APA_references">
			<h3>References:</h3>
			<p>
				Arpaci-Dusseau, R. H., &amp; Arpaci-Dusseau, A. C. (2016, July 20). The Abstraction: The Process. Retrieved from <a href="http://pages.cs.wisc.edu/~remzi/OSTEP/cpu-intro.pdf"><code>http://pages.cs.wisc.edu/~remzi/OSTEP/cpu-intro.pdf</code></a>
			</p>
		</div>
	</blockquote>
	<blockquote>
		<p>
			Several articles provide advice on Web design that is contradictory to the <a href="https://www.w3.org/TR/WCAG21/">$a[W3C]&apos;s Web Content Accessibility Guidelines</a>.
			These guidelines exist for a reason, and any advice that contradicts them, no matter how popular, cannot really be considered a best practice of the field.
			However, some articles with good advice on Web design do exist if you take the time to search for them.
		</p>
		<h3>Content</h3>
		<p>
			People reading your pages aren&apos;t looking for online books.
			They want to get the information they came for and leave.
			Keeping your content concise helps them find what they&apos;re after.
			Headings also break up walls of text nicely, and help readers find just the part they&apos;re looking for.
			Put your most important content at the beginning.
			Don&apos;t try to use interesting details and cliffhangers to get your reader to read the whole article; the won&apos;t do it, and will just leave faster.
			Get straight to the point, then add supporting details near the end for those that want to read that far.
			Use proper formatting and markup.
			Important information can be bolded using $a[CSS] and the <code>&lt;strong/&quot;</code> tag, for example.
			Information that makes sense as a list should be formatted as one too.
			Make sure there&apos;s enough space between paragraphs.
			Otherwise, your content will look like a wall of text and it&apos;ll be easy for your readers to lose their place (Gube, 2011).
			Gube also mentions making use of $a[CSS] for visited hyperlinks and making use of images.
			As long as you don&apos;t go too wild with the $a[CSS], that&apos;s a good idea.
			It helps readers to know which places they&apos;ve been to already.
			However, images should be used very carefully; some readers are visually impaired, cognitively impaired, or on a slow Internet connection.
			Any information that&apos;s made available in image form should <strong>*also*</strong> be made in text form.
		</p>
		<h3>Navigation</h3>
		<p>
			Navigation needs to be in an expected place so users can find it without even really looking for it.
			If a user has to put in <strong>*any*</strong> effort to find the main navigation menu, you did something wrong.
			The two standard places in which navigation menus are found is along the top of the page and along the left side.
			Due to the simplicity of <a href="https://y.st./">my website</a>&apos;s layout, I put the navigation menu at the top.
			That allows me to use very minimal $a[CSS] to keep it looking good and makes submenus (on the pages that have them) a breeze to put together.
			Left-side menus are highly viable though if you either don&apos;t have submenus or you don&apos;t mind getting fancy with the markup (for example, using nested lists).
			My navigation menus are added to the pages via my page-compilation scripts though, so such nesting would be a bit of a pain to code with very little actually gained from it.
			Top navigation menus also look equally at home on large and small pages alike, while left-side navigation menus look better on some pages than others.
			If you&apos;re looking for search engine optimisation, generic navigation link labels can be a problem.
			Using the correct key words in your navigation menu can boost your apparent relevancy to search engines without preventing your readers from finding their way(Crestodina, n.d.).
		</p>
		<p>
			Drop-down menus are a problem on multiple levels.
			First of all, they&apos;re clunky and hide information from view.
			We can read faster than we can manipulate the cursor, so dropdown menus slow us down considerably.
			But also, they&apos;re often implemented in JavaScript.
			This means that people, such as myself, that keep JavaScript disabled, won&apos;t be able to navigate your website.
			I also know people that use text-based Web browsers; these people can&apos;t use your JavaScript-based navigation menus either.
			Avoiding drop-down menus might tempt you to pack a tonne of links into the visible navigation, but that&apos;s a mistake as well.
			Having too many options displayed together can distract the reader, and keep them from seeing the link they&apos;re after.
			Try putting important links in the main navigation, then linking from those category main pages to the needed subpages.
			Placement of your navigation items in the menu also has an impact.
			Links in the centre are less likely to be seen than those on the ends, so the links placed there should be the ones of lesser importance(Crestodina, n.d.).
		</p>
		<div class="APA_references">
			<h3>References:</h3>
			<p>
				Crestodina, A. (n.d.). Are You Making These Common Website Navigation Mistakes? Retrieved from <a href="https://blog.kissmetrics.com/common-website-navigation-mistakes/"><code>https://blog.kissmetrics.com/common-website-navigation-mistakes/</code></a>
			</p>
			<p>
				Gube, J. (2011, September 12). 7 Best Practices for Improving Your Website&apos;s Usability. Retrieved from <a href="http://mashable.com/2011/09/12/website-usability-tips/"><code>http://mashable.com/2011/09/12/website-usability-tips/</code></a>
			</p>
		</div>
	</blockquote>
	<p>
		Before, I mentioned that I&apos;d copy my Wix-created website to a subdirectory of my main website once I finished building it.
		However, that&apos;s not going to work at all.
		Wix is a horrid system to build a website with.
		I already knew that.
		However, what I didn&apos;t know is that websites built using Wix are almost as bad as the Wix website builder itself.
		My entire website I&apos;m building for class is completely blank unless JavaScript is enabled.
		I can&apos;t copy anything, as none of this code is actually something I built.
		It&apos;s all some strange template and data-loading code.
		There&apos;s a way to coax Firefox into spitting out $a[XHTML] code representing the current state of the $a[DOM], but the output is such a mess due to how Wix is set up ...
		It&apos;s honestly not worth trying to clean it up and archive it.
		I&apos;m just going to archive a simplified, trimmed-down version, built from only the text I input and none of the layout information.
	</p>
</section>
END
);
